home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Plus Special 23
/
AMIGAplus Sonderheft 23 (2000)(Falke)(DE)[!].iso
/
Updates
/
Librarys
/
MMULib
/
ReadMe
< prev
next >
Wrap
Text File
|
1999-12-04
|
60KB
|
1,434 lines
The mmu.library project © 1998,99 the mmu.library development group, THOR
-----------------------------------------------------------------------------
Release 41.2
---------------
- The MMU Library build-in AddMem failed in case the base or length
were not aligned to 64K boundaries. It now rounds to the next 64K
boarders such that the supplied area is at least mounted partially.
- The idea to disable the TTx registers in the mmu.library was
unfortunately not a very smart idea as it broke the code on some
machines. Re-established the old rule with the only exception that
the TTx registers are initialized for the EC040.
- The ColdReboot() patch of the 68040.library used the MMU registers
even on a system without MMU. Fixed.
- MuMove4K checks now all libraries, devices, ports, resources and
resident modules whether they violate the 8K boundary.
- 68040.library: Forgot to disable the caches in ColdReboot().
- 68040.library: The motorola OpErr handler did not consider tracing
correctly. Fixed.
- Finally wrote and included the 68020.library and the 68030.library,
hence "FPU" will work on these machines.
- Updated MuGuardianAngel: Added a new keyword "DUMPWALL" that prints
the contents of a broken mung-wall and of broken memory cookies.
Release 41.1
---------------
- ScanMMUPort was broken and scanned for the wrong port. *Sigh*
This release should work better on Blizzard boards.
- AddMemList() uses now RebuildTreesA() to rebuild user and
supervisor tables at once and is therefore a bit more error
tolerant.
- The mmu.library will now support CachePreDMA/CachePostDMA for
the EC040 and EC060 processors as well.
- The 68040.library will now disable the TTx registers manually
such that the "generic" board does no longer require an
ENVARC:MMU-Configuration file.
- The 68040.library will now enable copyback caches for the EC040.
- Some of the MuTools did not unload properly if loaded from the workbench,
fixed.
- The MuTools are now a bit more error tolerant due to a new function in the
V41 mmu.library which gets used.
Release 40.60
-------------
- fixed the shutdown code of MGA, thanks to Stephan!
- disabled a kludge in the mmu.library which write protected
a kickstart image at 0x00200000 and up by checking the name
of execbase. This kludge might have conflicted with some softkickers.
- Because people tend not to read guides, I added the
arguments "WRITEPROTECTED" and "INVALID" to the library build-in
"SetCacheMode". Note that they work different to what "MuSetCacheMode"
does. Here, "WRITEPROTECTED" and "INVALID" are just aliases to "ROM"
and "BLANK", hence enable the most defensive protection strategy.
- Added a new LVO "RebuildTreesA" which is "officially" not yet
existing and will be documented in V41. More LVOs might be added up
to V41, but please *DO NOT* yet call them as they did not exist
in V40.50.
- Fixed the installation script, due to a typo the P5 MMU boot hack
was not detected.
- Fixed the P5Detect program which just looked to the wrong
identification resources. Ooops. Installation on "non-standard"
boards should be smoother now.
- Fixed a bug in the disassembler.library which disassembled the
lea (offset.L,pc)
wrong. The offset was wrong by two bytes.
- The release number in the MuForce guide was wrong.
- When will people finally learn to read the FAQ? *Sigh*
In case MuFastZero complains "The zero page is already remapped",
---> READ THE GUIDE. <---
Release 40.51.1
-------------
- disabled the layers.library kludge for MuGuardianAngel if V40
is found active. It is luckely no longer required.
Release 40.51
-------------
- fixed a bug in the 68060 startup logic which left the MMU disabled
in case it was disabled before. This made the custom 68060.library
useless.
- included the 40.17ß3 release of Carten Schlote's 68060.library
which (for the first time) makes use of the MMU.library.
Installation of this library requires some care as IT DOES NOT automatically
auto-detect P5 hardware and special setup magic for this hardware. This is
not because the library is "broken" in some sense, but because P5 didn't
follow the CBM guidelines when designing their hardware. Therefore, an
experimental installation script has been written. This script must be
run as follows:
- Unpack the archive to disk,
- Enter the following commands:
cd <MMULib>/Install ;where <MMULib> is the directory you unpacked this
;archive to
SYS:Rexxc/rx BuildMMUConfig.rexx ENVARC:MMU-Configuration
- The last command builds the MMU configuration and writes it
to ENVARC:MMU-Configuration. It might also copy ScanMMUPort
to LIBS:MMU. This is an external setup command for the library
and might or might not be required. Older P5 hardware does *not*
require it (I would guess that this is explicitly for the
Blizzards, but I'm not sure).
Non-P5 hardware will not require it at all.
You might want to hand-edit or optimize this script if you need,
as it will contain several optimizations for graphics cards and
other known boards.
- KEEP THE OLD 68060.library IN A SAFE PLACE.
- Make sure to install the 40.51 edition of the mmu.library
- Copy the 68060.library to LIBS:
- Reboot the computer and wish the new library luck. (-:
This edition of the '060 lib does *not yet* include correct VMM management
and FPU control functions (hence, C:FPU will not yet work). It is shorter
and costs less memory because it leaves the MMU setup to the mmu.library.
(Note that this release contains still debugging information).
In case the installation failed:
- Make sure the mathieedoubbas.library you're using is truely the
official 38.x or the patched and bugfixed 39.1. Some other third-
party products may fail to work correctly if the 68060 support
code is not yet loaded.
In case running the library fails (i.e. system doesn't boot):
- Make sure LIBS:mmu/ScanMMUPort is really available at boot-up
- Please re-boot the computer without the startup-sequence,
- Keep ENVARC:MMU-Configuration in a safe place,
- Re-install the old 68060.library.
- Boot the computer again,
- Run "MuScan" and keep the output.
Then, please sent me the output of MuScan, and the ENVARC:MMU-Configuration
file with a tiny note what exactly happened (or did not happen).
Release 40.50
--------------
- added external command scanning in case a setup command is
not found "resident".
- included Richard Körber's PatchWork and Olaf Barthel's
Sashimi. The "PatchWork" edition is *NEW* and *NOT YET AVAILABLE*
otherwise. Big "thank you" to Richard for updating it for this
archive. Big thanks to Olaf Barthel for allowing me to include
his "Sashimi" in the archive.
- bumped the version number.
- Final release.
Release 0.48
--------------
- mmu.library: Added a new command in the MMU-Configuration file,
"DescriptorCacheInhibit". It controls whether the MMU library
should disable the data cache for the descriptors. This is by
default OFF as this feature means more trouble for the library,
and is not required for using the library. However, this might
be a workaround for programs that hack the MMU table themselves,
which is not supported anyhow. Set it to "ON" if you MUST use
these programs.
- Added another VMM support function.
- MuGuardianAngel: The "memory header" output was broken, fixed.
Added more security checks, MuGuardianAngel will warn you in
case its function entries have been patched (which is not
supported)
- MuGuardianAngel: Added automatic stack checking within the
memory allocation functions - an overrun stack seems to be the
most common source of MuGuardianAngel problems. MuGuardianAngel
will now detect an "nearly out of stack" condition in the memory
handling, and will provide an "emergency" stack in case this
happens. It will then generate a warning, regardless of whether
stack snooping is enabled or not.
Interestingly, the RAM-Handler and the FastFilingSystem are the
most common sources of stack-overflows. This should be fixed